home *** CD-ROM | disk | FTP | other *** search
- Path: news99.sunet.se!umdac!news
- From: sagge@ts.umu.se (Mattias Sandgren)
- Newsgroups: comp.sys.amiga.applications,demon.tech.amiga,comp.sys.amiga.datacomm
- Subject: Re: Is MUI processor intensive?
- Date: 10 Feb 1996 18:52:42 GMT
- Organization: University of Umea, Sweden
- Message-ID: <1671.6614T1176T628@ts.umu.se>
- References: <9602030235.AA00575@sliver.demon.co.uk>
- NNTP-Posting-Host: ipcs3-2.modem.umu.se
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP) *UNREGISTERED*
-
-
- On 03-Feb-96 02:35:51, Mark wrote:
-
- >Henning Hucke (h_hucke@hucke.wob.tpl.de) wrote:
- >: Hmpf! What should be CPU-intensiv with MUI? At least as long as you don't
- >: have to resize the windwo all along or redraw window contents with Gadget
- >: inlays (like with HTML-Forms)? In other words: as long as there is
- >: nothing which causes the layout to be recalculated.
-
- >: On a normal 2000 or 600 the serial interface itself can cause such a load
- >: even with 19.2 Kbs.
-
- >All I can say then, the Amiga was never that great as I've seen
- >a Texas Instruments 99/4a do 19.2K. For those who don't know what
- >a TI99/4a was, it came out around 1982, had 16K RAM and used audio
- >tape to load and save.
-
- >My point is simple; an A600 should be able to sustain 19.2K baud
- >but it can't when I'm running AVM and MUI. I've killed off all
- >unnecessary progs from startup-sequence and user-startup. I've
- >used a 2 colour screen and also used a blanker. Something sucks
- >and I reckon it's MUI with all those libraries it opens.
-
- Nope, don't think so. You see, no task is eating CPU unless
- it has to. MUI certainly doesn't perform operations all the
- time. If a window is open and nothing is beeing computed
- somewhere, the CPU usage MUI creates should be close to zero
- as no window needs redrawing or the like. The blanker
- follows the same principle; it checks the input stream for
- inactivity and only makes a few operations when you press a
- mouse button or press a key. The problem is most probably a
- noisy line or a bad serial port, as the serial port is
- unbuffered it's even more so on an A600. My A1200/030@50MHz
- copes with 57600 easily.
-
-
- --
- Mattias Sandgren (sagge@ts.umu.se)
-
-